OEM PI Server

A full backup is appropriate when the disk crashes or there is an issue with the PI Server itself. The steps below provide information on restoring a full backup of the OEM PI Server for Sigmafine; it is the same procedure available in the PI Server System Management Guide. Note that if the problem you are experiencing is clearly only with the data, start from step 3 listed in the steps below.

To restore a full backup:

Note: This procedure assumes the operating system was reinstalled and has no knowledge of a previous installation.

1. Disconnect the node from the network.

2. Reinstall PI.

   The same version of the PI Server should be installed, as data file formats may change between versions. Therefore, it is important to install the same version that ran at time of last backup.

3. Start PI and verify that it is working properly.

4. Stop PI.

5. Verify that PI is not running before proceeding to the next step.

6. With the exception of 'pisubsys.cfg', restore the files that were backed up from the original PI\dat\ directory to the new PI\dat\ directory.

7. Restore all the message log files ("pimsg_xxxxxxx.dat") to the PI\log directory.

8. Restore the archives to the proper directory (by default PI\dat).

9. Restore any of the batch files from the PI\adm directory that had been customized to start and stop PI (such as 'pisrvsitestart.bat', etc.).

10. Connect the PI Server to the network.

11. Verify that the PI Server is reachable from clients on the network.